Digital broadcasting system and method of processing data in digital broadcasting system

ABSTRACT

A digital broadcasting system and a data processing method are disclosed. A receiver receives a broadcast signal including mobile service data and main service data. A known data detector detects known data from the broadcast signal. An equalizer performs channel equalization on the mobile service data received by means of the detected known data. An RS frame decoder acquires an RS frame from the channel-equalized mobile service data. A management processor extracts a Generic Stream Encapsulation (GSE) packet from a GSE Base Band (BB) constructing one row of the RS frame, and calculates an IP datagram from the extracted GSE packet. A presentation processor displays broadcast data using data contained in the calculated IP datagram.

This application is a continuation of U.S. application Ser. No.14/534,990, filed on Nov. 6, 2014, currently pending, which is acontinuation of U.S. Application Ser. No. 14/191,019, filed on Feb. 26,2014, now U.S. Pat. No. 8,917,727, which is a continuation of U.S.application Ser. No. 13/069,268, filed on Mar. 22, 2011, now U.S. Pat.No. 8,687,635, which is a continuation of U.S. application Ser. No.12/235,583, filed on Sep. 22, 2008, now U.S. Pat. No. 7,936,786, whichclaims the benefit of earlier filing date and right of priority toKorean Patent Application No. 10-2008-0092361, filed on Sep. 19, 2008,and also claims the benefit of U.S. Provisional Application Ser. Nos.60/973,773, filed on Sep. 20, 2007, 60/974,084, filed on Sep. 21, 2007,60/977,379, filed on Oct. 4, 2007, 61/044,504, filed on Apr. 13, 2008,and 61/076,686, filed on Jun. 29, 2008, the contents of all of which arehereby incorporated by reference herein in their entireties.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to a digital broadcasting system, and moreparticularly, to a digital broadcasting system and a data processingmethod.

Discussion of the Related Art

The Vestigial Sideband (VSB) transmission mode, which is adopted as thestandard for digital broadcasting in North America and the Republic ofKorea, is a system using a single carrier method. Therefore, thereceiving performance of the digital broadcast receiving system may bedeteriorated in a poor channel environment. Particularly, sinceresistance to changes in channels and noise is more highly required whenusing portable and/or mobile broadcast receivers, the receivingperformance may be even more deteriorated when transmitting mobileservice data by the VSB transmission mode.

SUMMARY OF THE INVENTION

The present invention provides a data processing method comprising:receiving a broadcast signal including mobile service data and mainservice data; detecting known data from the broadcast signal; performingchannel equalization on the mobile service data received by means of thedetected known data; acquiring a Reed Solomon (RS) frame from thechannel-equalized mobile service data; extracting a Generic StreamEncapsulation (GSE) packet from a GSE Base Band (BB) constructing onerow of the RS frame, and calculating an IP datagram from the GSE packet;and displaying broadcast data using data contained in the calculated IPdatagram.

The mobile service data may configure a data group, in which the datagroup is segmented into several areas, a known data sequence is linearlyinserted into some areas from among the several areas, andinitialization data for initializing a memory contained in a Trellisencoder of a transmitter is located at a start part of the known datasequence; and N number of the known data sequences are inserted into thesome areas from among the several areas, and a transmission parameter isinserted between a first known data sequence and a second known datasequence from among the N known data sequences.

The calculating step may include: recovering a header of the IP datagramby releasing compression of data contained in a data field of the GSEpacket. The header of the IP datagram may be compressed by a RobustHeader Compression (ROHC).

The IP datagram is contained in a data field of at least one GSE packet.

In another aspect of the present invention, there is provided a dataprocessing method comprising: encapsulating an IP datagram includingmobile service data into at least one Generic Stream Encapsulation (GSE)packet; generating a mobile service data frame including the GSE packet;segmenting the generated mobile service data frame into data groups, andmultiplexing the data groups with main service data; modulating themultiplexed data groups and the main service data into a broadcastsignal; and transmitting the broadcast signal. The generating step mayinclude: forming a Base Band (BB) frame with the GSE packet; andgenerating the mobile service data frame by constructing the BB frame inrow units of the mobile service data frame.

The encapsulating step may include: compressing a header of the IPdatagram. The header of the IP datagram may be compressed by a RobustHeader Compression (ROHC).

In another aspect of the present invention, there is provided a digitalbroadcasting system comprising: a receiver for receiving a broadcastsignal including mobile service data and main service data; a known datadetector for detecting known data from the broadcast signal; anequalizer for performing channel equalization on the mobile service datareceived by means of the detected known data; a Reed Solomon (RS) framedecoder for acquiring a Reed Solomon (RS) frame from thechannel-equalized mobile service data; a management processor forextracting a Generic Stream Encapsulation (GSE) packet from a GSE BaseBand (BB) constructing one row of the RS frame, and calculating an IPdatagram from the extracted GSE packet; and a presentation processor fordisplaying broadcast data using data contained in the calculated IPdatagram.

The mobile service data may configure a data group, in which the datagroup is segmented into several areas, a known data sequence is linearlyinserted into some areas from among the several areas, andinitialization data for initializing a memory contained in a Trellisencoder of a transmitter is located at a start part of the known datasequence; and N number of the known data sequences are inserted into thesome areas from among the several areas, and a transmission parameter isinserted between a first known data sequence and a second known datasequence from among the N known data sequences.

The management processor may release compression of data contained in adata field of the GSE packet, and may recover a header of the IPdatagram. The management processor may release compression of the headerof the IP datagram on the basis of a Robust Header Compression (ROHC).

The management processor may calculate the IP datagram from a data fieldof at least one GSE packet.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention. In the drawings;

FIG. 1 illustrates a block diagram showing a general structure of adigital broadcasting receiving system according to an embodiment of thepresent invention;

FIG. 2 illustrates an exemplary structure of a data group according tothe present invention;

FIG. 3 illustrates an RS frame according to an embodiment of the presentinvention;

FIG. 4 illustrates an example of an MH frame structure for transmittingand receiving mobile service data according to the present invention;

FIG. 5 illustrates an example of a general VSB frame structure;

FIG. 6 illustrates a example of mapping positions of the first 4 slotsof a sub-frame in a spatial area with respect to a VSB frame;

FIG. 7 illustrates a example of mapping positions of the first 4 slotsof a sub-frame in a chronological (or time) area with respect to a VSBframe;

FIG. 8 illustrates an exemplary order of data groups being assigned toone of 5 sub-frames configuring an MH frame according to the presentinvention;

FIG. 9 illustrates an example of a single parade being assigned to an MHframe according to the present invention;

FIG. 10 illustrates an example of 3 parades being assigned to an MHframe according to the present invention;

FIG. 11 illustrates an example of the process of assigning 3 paradesshown in FIG. 10 being expanded to 5 sub-frames within an MH frame;

FIG. 12 illustrates a data transmission structure according to anembodiment of the present invention, wherein signaling data are includedin a data group so as to be transmitted;

FIG. 13 illustrates a hierarchical signaling structure according to anembodiment of the present invention;

FIG. 14 illustrates an exemplary FIC body format according to anembodiment of the present invention;

FIG. 15 illustrates an exemplary bit stream syntax structure withrespect to an FIC segment according to an embodiment of the presentinvention;

FIG. 16 illustrates an exemplary bit stream syntax structure withrespect to a payload of an FIC segment according to the presentinvention, when an FIC type field value is equal to ‘0’;

FIG. 17 illustrates an exemplary bit stream syntax structure of aservice map table according to the present invention;

FIG. 18 illustrates an exemplary bit stream syntax structure of an MHaudio descriptor according to the present invention;

FIG. 19 illustrates an exemplary bit stream syntax structure of an MHRTP payload type descriptor according to the present invention;

FIG. 20 illustrates an exemplary bit stream syntax structure of an MHcurrent event descriptor according to the present invention;

FIG. 21 illustrates an exemplary bit stream syntax structure of an MHnext event descriptor according to the present invention;

FIG. 22 illustrates an exemplary bit stream syntax structure of an MHsystem time descriptor according to the present invention;

FIG. 23 illustrates segmentation and encapsulation processes of aservice map table according to the present invention; and

FIG. 24 illustrates a flow chart for accessing a virtual channel usingFIC and SMT according to the present invention.

FIG. 25 illustrates a block diagram showing a general structure of adigital broadcasting receiving system according to another embodiment ofthe present invention;

FIG. 26 is a structural diagram illustrating a Reed Solomon (RS) frameaccording to another embodiment of the present invention;

FIG. 27 shows the relationship between Protocol Data Units (PDUs) andGeneric Stream Encapsulation (GSE) packets according to the presentinvention;

FIG. 28 shows a header of the Generic Stream Encapsulation (GSE) packetaccording to the present invention;

FIG. 29 is a conceptual diagram illustrating a method for constructingthe GSE packet according to the present invention; and

FIG. 30 is a flow chart illustrating a data processing method accordingto the present invention.

FIG. 31 is a flow chart illustrating a method of processing broadcastdata in a transmitter according to an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. At this time, it is to be understood that the followingdetailed description of the present invention illustrated in thedrawings and described with reference to the drawings are exemplary andexplanatory and technical spirits of the present invention and mainfeatures and operation of the present invention will not be limited bythe following detailed description

Definition of Terms Used in the Present Invention

Although general terms, which are widely used considering functions inthe present invention, have been selected in the present invention, theymay be changed depending on intention of those skilled in the art,practices, or new technology. Also, in specific case, the applicant mayoptionally select the terms. In this case, the meaning of the terms willbe described in detail in the description part of the invention.Therefore, it is to be understood that the terms should be defined basedupon their meaning not their simple title and the whole description ofthe present invention.

Among the terms used in the description of the present invention, mainservice data correspond to data that can be received by a fixedreceiving system and may include audio/video (A/V) data. Morespecifically, the main service data may include A/V data of highdefinition (HD) or standard definition (SD) levels and may also includediverse data types required for data broadcasting. Also, the known datacorrespond to data pre-known in accordance with a pre-arranged agreementbetween the receiving system and the transmitting system.

Additionally, among the terms used in the present invention, “MH”corresponds to the initials of “mobile” and “handheld” and representsthe opposite concept of a fixed-type system. Furthermore, the MH servicedata may include at least one of mobile service data and handheldservice data, and will also be referred to as “mobile service data” forsimplicity. Herein, the mobile service data not only correspond to MHservice data but may also include any type of service data with mobileor portable characteristics. Therefore, the mobile service dataaccording to the present invention are not limited only to the MHservice data.

The above-described mobile service data may correspond to data havinginformation, such as program execution files, stock information, and soon, and may also correspond to A/V data. Most particularly, the mobileservice data may correspond to A/V data having lower resolution andlower data rate as compared to the main service data. For example, if anA/V codec that is used for a conventional main service corresponds to aMPEG-2 codec, a MPEG-4 advanced video coding (AVC) or scalable videocoding (SVC) having better image compression efficiency may be used asthe A/V codec for the mobile service. Furthermore, any type of data maybe transmitted as the mobile service data. For example, transportprotocol expert group (TPEG) data for broadcasting real-timetransportation information may be transmitted as the main service data.

Also, a data service using the mobile service data may include weatherforecast services, traffic information services, stock informationservices, viewer participation quiz programs, real-time polls andsurveys, interactive education broadcast programs, gaming services,services providing information on synopsis, character, background music,and filming sites of soap operas or series, services providinginformation on past match scores and player profiles and achievements,and services providing information on product information and programsclassified by service, medium, time, and theme enabling purchase ordersto be processed. Herein, the present invention is not limited only tothe services mentioned above.

In the present invention, the transmitting system provides backwardcompatibility in the main service data so as to be received by theconventional receiving system. Herein, the main service data and themobile service data are multiplexed to the same physical channel andthen transmitted.

Furthermore, the digital broadcast transmitting system according to thepresent invention performs additional encoding on the mobile servicedata and inserts the data already known by the receiving system andtransmitting system (e.g., known data), thereby transmitting theprocessed data.

Therefore, when using the transmitting system according to the presentinvention, the receiving system may receive the mobile service dataduring a mobile state and may also receive the mobile service data withstability despite various distortion and noise occurring within thechannel.

Receiving System

FIG. 1 illustrates a block diagram showing a general structure of adigital broadcasting receiving system according to an embodiment of thepresent invention. The digital broadcast receiving system according tothe present invention includes a baseband processor 100, a managementprocessor 200, and a presentation processor 300.

The baseband processor 100 includes an operation controller 110, a tuner120, a demodulator 130, an equalizer 140, a known sequence detector (orknown data detector) 150, a block decoder (or mobile handheld blockdecoder) 160, a promary Reed-Solomon (RS) frame decoder 170, a secondaryRS frame decoder 180, and a signaling decoder 190. The operationcontroller 110 controls the operation of each block included in thebaseband processor 100.

By tuning the receiving system to a specific physical channel frequency,the tuner 120 enables the receiving system to receive main service data,which correspond to broadcast signals for fixed-type broadcast receivingsystems, and mobile service data, which correspond to broadcast signalsfor mobile broadcast receiving systems. At this point, the tunedfrequency of the specific physical channel is down-converted to anintermediate frequency (IF) signal, thereby being outputted to thedemodulator 130 and the known sequence detector 140. The passbanddigital IF signal being outputted from the tuner 120 may only includemain service data, or only include mobile service data, or include bothmain service data and mobile service data.

The demodulator 130 performs self-gain control, carrier wave recovery,and timing recovery processes on the passband digital IF signal inputtedfrom the tuner 120, thereby modifying the IF signal to a basebandsignal. Then, the demodulator 130 outputs the baseband signal to theequalizer 140 and the known sequence detector 150. The demodulator 130uses the known data symbol sequence inputted from the known sequencedetector 150 during the timing and/or carrier wave recovery, therebyenhancing the demodulating performance.

The equalizer 140 compensates channel-associated distortion included inthe signal demodulated by the demodulator 130. Then, the equalizer 140outputs the distortion-compensated signal to the block decoder 160. Byusing a known data symbol sequence inputted from the known sequencedetector 150, the equalizer 140 may enhance the equalizing performance.Furthermore, the equalizer 140 may receive feed-back on the decodingresult from the block decoder 160, thereby enhancing the equalizingperformance.

The known sequence detector 150 detects known data place (or position)inserted by the transmitting system from the input/output data (i.e.,data prior to being demodulated or data being processed with partialdemodulation). Then, the known sequence detector 150 outputs thedetected known data position information and known data sequencegenerated from the detected position information to the demodulator 130and the equalizer 140. Additionally, in order to allow the block decoder160 to identify the mobile service data that have been processed withadditional encoding by the transmitting system and the main service datathat have not been processed with any additional encoding, the knownsequence detector 150 outputs such corresponding information to theblock decoder 160.

If the data channel-equalized by the equalizer 140 and inputted to theblock decoder 160 correspond to data processed with both block-encodingand trellis-encoding by the transmitting system (i.e., data within theRS frame, signaling data), the block decoder 160 may performtrellis-decoding and block-decoding as inverse processes of thetransmitting system. On the other hand, if the data channel-equalized bythe equalizer 140 and inputted to the block decoder 160 correspond todata processed only with trellis-encoding and not block-encoding by thetransmitting system (i.e., main service data), the block decoder 160 mayperform only trellis-decoding.

The signaling decoder 190 decoded signaling data that have beenchannel-equalized and inputted from the equalizer 140. It is assumedthat the signaling data inputted to the signaling decoder 190 correspondto data processed with both block-encoding and trellis-encoding by thetransmitting system. Examples of such signaling data may includetransmission parameter channel (TPC) data and fast information channel(FIC) data. Each type of data will be described in more detail in alater process. The FIC data decoded by the signaling decoder 190 areoutputted to the FIC handler 215. And, the TPC data decoded by thesignaling decoder 190 are outputted to the TPC handler 214.

Meanwhile, according to the present invention, the transmitting systemuses RS frames by encoding units. Herein, the RS frame may be dividedinto a primary RS frame and a secondary RS frame. However, according tothe embodiment of the present invention, the primary RS frame and thesecondary RS frame will be divided based upon the level of importance ofthe corresponding data.

The primary RS frame decoder 170 receives the data outputted from theblock decoder 160. At this point, according to the embodiment of thepresent invention, the primary RS frame decoder 170 receives only themobile service data that have been Reed-Solomon (RS)-encoded and/orcyclic redundancy check (CRC)-encoded from the block decoder 160.

Herein, the primary RS frame decoder 170 receives only the mobileservice data and not the main service data. The primary RS frame decoder170 performs inverse processes of an RS frame encoder (not shown)included in the digital broadcast transmitting system, therebycorrecting errors existing within the primary RS frame. Morespecifically, the primary RS frame decoder 170 forms a primary RS frameby grouping a plurality of data groups and, then, correct errors inprimary RS frame units. In other words, the primary RS frame decoder 170decodes primary RS frames, which are being transmitted for actualbroadcast services.

Additionally, the secondary RS frame decoder 180 receives the dataoutputted from the block decoder 160. At this point, according to theembodiment of the present invention, the secondary RS frame decoder 180receives only the mobile service data that have been RS-encoded and/orCRC-encoded from the block decoder 160. Herein, the secondary RS framedecoder 180 receives only the mobile service data and not the mainservice data. The secondary RS frame decoder 180 performs inverseprocesses of an RS frame encoder (not shown) included in the digitalbroadcast transmitting system, thereby correcting errors existing withinthe secondary RS frame. More specifically, the secondary RS framedecoder 180 forms a secondary RS frame by grouping a plurality of datagroups and, then, correct errors in secondary RS frame units. In otherwords, the secondary RS frame decoder 180 decodes secondary RS frames,which are being transmitted for mobile audio service data, mobile videoservice data, guide data, and so on.

Meanwhile, the management processor 200 according to an embodiment ofthe present invention includes an MH physical adaptation processor 210,an IP network stack 220, a streaming handler 230, a system information(SI) handler 240, a file handler 250, a multi-purpose internet mainextensions (MIME) type handler 260, and an electronic service guide(ESG) handler 270, and an ESG decoder 280, and a storage unit 290.

The MH physical adaptation processor 210 includes a primary RS framehandler 211, a secondary RS frame handler 212, an MH transport packet(TP) handler 213, a TPC handler 214, an FIC handler 215, and a physicaladaptation control signal handler 216.

The TPC handler 214 receives and processes baseband information requiredby modules corresponding to the MH physical adaptation processor 210.The baseband information is inputted in the form of TPC data. Herein,the TPC handler 214 uses this information to process the FIC data, whichhave been sent from the baseband processor 100.

The TPC data are transmitted from the transmitting system to thereceiving system via a predetermined region of a data group. The TPCdata may include at least one of an MH ensemble ID, an MH sub-framenumber, a total number of MH groups (TNoG), an RS frame continuitycounter, a column size of RS frame (N), and an FIC version number.

Herein, the MH ensemble ID indicates an identification number of each MHensemble carried in the corresponding channel. The MH sub-frame numbersignifies a number identifying the MH sub-frame number in an MH frame,wherein each MH group associated with the corresponding MH ensemble istransmitted. The TNoG represents the total number of MH groups includingall of the MH groups belonging to all MH parades included in an MHsub-frame.

The RS frame continuity counter indicates a number that serves as acontinuity counter of the RS frames carrying the corresponding MHensemble. Herein, the value of the RS frame continuity counter shall beincremented by 1 modulo 16 for each successive RS frame.

N represents the column size of an RS frame belonging to thecorresponding MH ensemble. Herein, the value of N determines the size ofeach MH TP.

Finally, the FIC version number signifies the version number of an FICbody carried on the corresponding physical channel.

As described above, diverse TPC data are inputted to the TPC handler 214via the signaling decoder 190 shown in FIG. 1. Then, the received TPCdata are processed by the TPC handler 214. The received TPC data mayalso be used by the FIC handler 215 in order to process the FIC data.

The FIC handler 215 processes the FIC data by associating the FIC datareceived from the baseband processor 100 with the TPC data.

The physical adaptation control signal handler 216 collects FIC datareceived through the FIC handler 215 and SI data received through RSframes. Then, the physical adaptation control signal handler 216 usesthe collected FIC data and SI data to configure and process IP datagramsand access information of mobile broadcast services. Thereafter, thephysical adaptation control signal handler 216 stores the processed IPdatagrams and access information to the storage unit 290.

The primary RS frame handler 211 identifies primary RS frames receivedfrom the primary RS frame decoder 170 of the baseband processor 100 foreach row unit, so as to configure an MH TP. Thereafter, the primary RSframe handler 211 outputs the configured MH TP to the MH TP handler 213.

The secondary RS frame handler 212 identifies secondary RS framesreceived from the secondary RS frame decoder 180 of the basebandprocessor 100 for each row unit, so as to configure an MH TP.Thereafter, the secondary RS frame handler 212 outputs the configured MHTP to the MH TP handler 213.

The MH transport packet (TP) handler 213 extracts a header from each MHTP received from the primary RS frame handler 211 and the secondary RSframe handler 212, thereby determining the data included in thecorresponding MH TP. Then, when the determined data correspond to SIdata (i.e., SI data that are not encapsulated to IP datagrams), thecorresponding data are outputted to the physical adaptation controlsignal handler 216. Alternatively, when the determined data correspondto an IP datagram, the corresponding data are outputted to the IPnetwork stack 220.

The IP network stack 220 processes broadcast data that are beingtransmitted in the form of IP datagrams. More specifically, the IPnetwork stack 220 processes data that are inputted via user datagramprotocol (UDP), real-time transport protocol (RTP), real-time transportcontrol protocol (RTCP), asynchronous layered coding/layered codingtransport (ALC/LCT), file delivery over unidirectional transport(FLUTE), and so on. Herein, when the processed data correspond tostreaming data, the corresponding data are outputted to the streaminghandler 230. And, when the processed data correspond to data in a fileformat, the corresponding data are outputted to the file handler 250.Finally, when the processed data correspond to SI-associated data, thecorresponding data are outputted to the SI handler 240.

The SI handler 240 receives and processes SI data having the form of IPdatagrams, which are inputted to the IP network stack 220. When theinputted data associated with SI correspond to MIME-type data, theinputted data are outputted to the MIME-type handler 260. The MIME-typehandler 260 receives the MIME-type SI data outputted from the SI handler240 and processes the received MIME-type SI data.

The file handler 250 receives data from the IP network stack 220 in anobject format in accordance with the ALC/LCT and FLUTE structures. Thefile handler 250 groups the received data to create a file format.Herein, when the corresponding file includes ESG, the file is outputtedto the ESG handler 270. On the other hand, when the corresponding fileincludes data for other file-based services, the file is outputted tothe presentation controller 330 of the presentation processor 300.

The ESG handler 270 processes the ESG data received from the filehandler 250 and stores the processed ESG data to the storage unit 290.Alternatively, the ESG handler 270 may output the processed ESG data tothe ESG decoder 280, thereby allowing the ESG data to be used by the ESGdecoder 280.

The storage unit 290 stores the system information (SI) received fromthe physical adaptation control signal handler 210 and the ESG handler270 therein. Thereafter, the storage unit 290 transmits the stored SIdata to each block.

The ESG decoder 280 either recovers the ESG data and SI data stored inthe storage unit 290 or recovers the ESG data transmitted from the ESGhandler 270. Then, the ESG decoder 280 outputs the recovered data to thepresentation controller 330 in a format that can be outputted to theuser.

The streaming handler 230 receives data from the IP network stack 220,wherein the format of the received data are in accordance with RTPand/or RTCP structures. The streaming handler 230 extracts audio/videostreams from the received data, which are then outputted to theaudio/video (A/V) decoder 310 of the presentation processor 300. Theaudio/video decoder 310 then decodes each of the audio stream and videostream received from the streaming handler 230.

The display module 320 of the presentation processor 300 receives audioand video signals respectively decoded by the A/V decoder 310. Then, thedisplay module 320 provides the received audio and video signals to theuser through a speaker and/or a screen.

The presentation controller 330 corresponds to a controller managingmodules that output data received by the receiving system to the user.

The channel service manager 340 manages an interface with the user,which enables the user to use channel-based broadcast services, such aschannel map management, channel service connection, and so on.

The application manager 350 manages an interface with a user using ESGdisplay or other application services that do not correspond tochannel-based services.

Meanwhile, The streaming handler 230 may include a buffer temporarilystoring audio/video data. The digital broadcasting reception systemperiodically sets reference time information to a system time clock, andthen the stored audio/video data can be transferred to A/V decoder 310at a constant bitrate. Accordingly, the audio/video data can beprocessed at a bitrate and audio/video service can be provided.

FIG. 31 illustrates a method of processing broadcast data in atransmitter according to an embodiment of the invention.

Data Format Structure

Meanwhile, the data structure used in the mobile broadcasting technologyaccording to the embodiment of the present invention may include a datagroup structure and an RS frame structure, which will now be describedin detail.

FIG. 2 illustrates an exemplary structure of a data group according tothe present invention.

FIG. 2 shows an example of dividing a data group according to the datastructure of the present invention into 10 MH blo In this example, eachMH block has the length of 16 segments. Referring to FIG. 2, only the RSparity data are allocated to portions of the first 5 segments of the MHblock (B1) and the last 5 segments of the MH block 10 (B10). The RSparity data are excluded in regions A to D of the data group.

More specifically, when it is assumed that one data group is dividedinto regions A, B, C, and D, each MH block may be included in any one ofregion A to region D depending upon the characteristic of each MH blockwithin the data group.

Herein, the data group is divided into a plurality of regions to be usedfor different purposes. More specifically, a region of the main servicedata having no interference or a very low interference level may beconsidered to have a more resistant (or stronger) receiving performanceas compared to regions having higher interference levels. Additionally,when using a system inserting and transmitting known data in the datagroup, wherein the known data are known based upon an agreement betweenthe transmitting system and the receiving system, and when consecutivelylong known data are to be periodically inserted in the mobile servicedata, the known data having a predetermined length may be periodicallyinserted in the region having no interference from the main service data(i.e., a region wherein the main service data are not mixed). However,due to interference from the main service data, it is difficult toperiodically insert known data and also to insert consecutively longknown data to a region having interference from the main service data.

Referring to FIG. 2, MH block 4 (B4) to MH block 7 (B7) correspond toregions without interference of the main service data. MH block 4 (B4)to MH block 7 (B7) within the data group shown in FIG. 2 correspond to aregion where no interference from the main service data occurs. In thisexample, a long known data sequence is inserted at both the beginningand end of each MH block. In the description of the present invention,the region including MH block 4 (B4) to MH block 7 (B7) will be referredto as “region A (=B4+B5+B6+B7)”. As described above, when the data groupincludes region A having a long known data sequence inserted at both thebeginning and end of each MH block, the receiving system is capable ofperforming equalization by using the channel information that can beobtained from the known data. Therefore, the strongest equalizingperformance may be yielded (or obtained) from one of region A to regionD.

In the example of the data group shown in FIG. 2, MH block 3 (B3) and MHblock 8 (B8) correspond to a region having little interference from themain service data. Herein, a long known data sequence is inserted inonly one side of each MH block B3 and B8. More specifically, due to theinterference from the main service data, a long known data sequence isinserted at the end of MH block 3 (B3), and another long known datasequence is inserted at the beginning of MH block 8 (B8). In the presentinvention, the region including MH block 3 (B3) and MH block 8 (B8) willbe referred to as “region B (=B3+B8)”. As described above, when the datagroup includes region B having a long known data sequence inserted atonly one side (beginning or end) of each MH block, the receiving systemis capable of performing equalization by using the channel informationthat can be obtained from the known data. Therefore, a strongerequalizing performance as compared to region C/D may be yielded (orobtained).

Referring to FIG. 2, MH block 2 (B2) and MH block 9 (B9) correspond to aregion having more interference from the main service data as comparedto region B. A long known data sequence cannot be inserted in any sideof MH block 2 (B2) and MH block 9 (B9). Herein, the region including MHblock 2 (B2) and MH block 9 (B9) will be referred to as “region C(=B2+B9)”.

Finally, in the example shown in FIG. 2, MH block 1 (B1) and MH block 10(B10) correspond to a region having more interference from the mainservice data as compared to region C. Similarly, a long known datasequence cannot be inserted in any side of MH block 1 (B1) and MH block10 (B10). Herein, the region including MH block 1 (B1) and MH block 10(B10) will be referred to as “region D (=B1+B10)”. Since region C/D isspaced further apart from the known data sequence, when the channelenvironment undergoes frequent and abrupt changes, the receivingperformance of region C/D may be deteriorated.

Additionally, the data group includes a signaling information areawherein signaling information is assigned (or allocated).

In the present invention, the signaling information area may start fromthe 1^(st) segment of the 4^(th) MH block (B4) to a portion of the2^(nd) segment.

According to an embodiment of the present invention, the signalinginformation area for inserting signaling information may start from the1^(st) segment of the 4^(th) MH block (B4) to a portion of the 2^(nd)segment. More specifically, 276(=207+69) bytes of the 4^(th) MH block(B4) in each data group are assigned as the signaling information area.In other words, the signaling information area consists of 207 bytes ofthe 1^(st) segment and the first 69 bytes of the 2^(nd) segment of the4^(th) MH block (B4). The 1^(st) segment of the 4^(th) MH block (B4)corresponds to the 17^(th) or 173^(rd) segment of a VSB field.

Herein, the signaling information may be identified by two differenttypes of signaling channels: a transmission parameter channel (TPC) anda fast information channel (FIC).

Herein, the TPC data may include at least one of an MH ensemble ID, anMH sub-frame number, a total number of MH groups (TNoG), an RS framecontinuity counter, a column size of RS frame (N), and an FIC versionnumber. However, the TPC data (or information) presented herein aremerely exemplary. And, since the adding or deleting of signalinginformation included in the TPC data may be easily adjusted and modifiedby one skilled in the art, the present invention will, therefore, not belimited to the examples set forth herein. Furthermore, the FIC isprovided to enable a fast service acquisition of data receivers, and theFIC includes cross layer information between the physical layer and theupper layer(s). For example, when the data group includes 6 known datasequences, as shown in FIG. 2, the signaling information area is locatedbetween the first known data sequence and the second known datasequence. More specifically, the first known data sequence is insertedin the last 2 segments of the 3^(rd) MH block (B3), and the second knowndata sequence in inserted in the 2^(nd) and 3^(rd) segments of the4^(th) MH block (B4). Furthermore, the 3^(rd) to 6^(th) known datasequences are respectively inserted in the last 2 segments of each ofthe 4^(th), 5^(th), 6^(th), and 7^(th) MH blocks (B4, B5, B6, and B7).The 1^(st) and 3^(rd) to 6^(th) known data sequences are spaced apart by16 segments.

FIG. 3 illustrates an RS frame according to an embodiment of the presentinvention.

The RS frame shown in FIG. 3 corresponds to a collection of one or moredata groups. The RS frame is received for each MH frame in a conditionwhere the receiving system receives the FIC and processes the receivedFIC and where the receiving system is switched to a time-slicing mode sothat the receiving system can receive MH ensembles including ESG entrypoints. Each RS frame includes IP streams of each service or ESG, andSMT section data may exist in all RS frames.

The RS frame according to the embodiment of the present inventionconsists of at least one MH transport packet (TP). Herein, the MH TPincludes an MH header and an MH payload.

The MH payload may include mobile service data as wekk as signalingdata. More specifically, an MH payload may include only mobile servicedata, or may include only signaling data, or may include both mobileservice data and signaling data.

According to the embodiment of the present invention, the MH header mayidentify (or distinguish) the data types included in the MH payload.More specifically, when the MH TP includes a first MH header, thisindicates that the MH payload includes only the signaling data. Also,when the MH TP includes a second MH header, this indicates that the MHpayload includes both the signaling data and the mobile service data.Finally, when MH TP includes a third MH header, this indicates that theMH payload includes only the mobile service data.

In the example shown in FIG. 3, the RS frame is assigned with IPdatagrams (IP datagram 1 and IP datagram 2) for two service types.

The IP datagram in the MH-TP in the RS frame may include reference timeinformation (for example, network time stamp (NTP)), the detaileddescription for the reference time information will be disclosed bybeing referred to FIGS. 25 to 29.

Data Transmission Structure

FIG. 4 illustrates a structure of a MH frame for transmitting andreceiving mobile service data according to the present invention.

In the example shown in FIG. 4, one MH frame consists of 5 sub-frames,wherein each sub-frame includes 16 slots. In this case, the MH frameaccording to the present invention includes 5 sub-frames and 80 slots.

Also, in a packet level, one slot is configured of 156 data packets(i.e., transport stream packets), and in a symbol level, one slot isconfigured of 156 data segments. Herein, the size of one slotcorresponds to one half (½) of a VSB field. More specifically, since one207-byte data packet has the same amount of data as a data segment, adata packet prior to being interleaved may also be used as a datasegment. At this point, two VSB fields are grouped to form a VSB frame.

FIG. 5 illustrates an exemplary structure of a VSB frame, wherein oneVSB frame consists of 2 VSB fields (i.e., an odd field and an evenfield). Herein, each VSB field includes a field synchronization segmentand 312 data segments. The slot corresponds to a basic time unit formultiplexing the mobile service data and the main service data. Herein,one slot may either include the mobile service data or be configuredonly of the main service data.

If the first 118 data packets within the slot correspond to a datagroup, the remaining 38 data packets become the main service datapackets. In another example, when no data group exists in a slot, thecorresponding slot is configured of 156 main service data packets.

Meanwhile, when the slots are assigned to a VSB frame, an off-set existsfor each assigned position.

FIG. 6 illustrates a mapping example of the positions to which the first4 slots of a sub-frame are assigned with respect to a VSB frame in aspatial area. And, FIG. 7 illustrates a mapping example of the positionsto which the first 4 slots of a sub-frame are assigned with respect to aVSB frame in a chronological (or time) area.

Referring to FIG. 6 and FIG. 7, a 38^(th) data packet (TS packet #37) ofa 1^(st) slot (Slot #0) is mapped to the 1^(st) data packet of an oddVSB field. A 38^(th) data packet (TS packet #37) of a 2^(nd) slot (Slot#1) is mapped to the 157^(th) data packet of an odd VSB field. Also, a38^(th) data packet (TS packet #37) of a 3^(rd) slot (Slot #2) is mappedto the 1^(st) data packet of an even VSB field. And, a 38^(th) datapacket (TS packet #37) of a 4^(th) slot (Slot #3) is mapped to the157^(th) data packet of an even VSB field. Similarly, the remaining 12slots within the corresponding sub-frame are mapped in the subsequentVSB frames using the same method.

FIG. 8 illustrates an exemplary assignment order of data groups beingassigned to one of 5 sub-frames, wherein the 5 sub-frames configure anMH frame. For example, the method of assigning data groups may beidentically applied to all MH frames or differently applied to each MHframe. Furthermore, the method of assigning data groups may beidentically applied to all sub-frames or differently applied to eachsub-frame. At this point, when it is assumed that the data groups areassigned using the same method in all sub-frames of the corresponding MHframe, the total number of data groups being assigned to an MH frame isequal to a multiple of ‘5’.

According to the embodiment of the present invention, a plurality ofconsecutive data groups is assigned to be spaced as far apart from oneanother as possible within the MH frame. Thus, the system can be capableof responding promptly and effectively to any burst error that may occurwithin a sub-frame.

For example, when it is assumed that 3 data groups are assigned to asub-frame, the data groups are assigned to a 1^(st) slot (Slot #0), a5^(th) slot (Slot #4), and a 9^(th) slot (Slot #8) in the sub-frame,respectively. FIG. 8 illustrates an example of assigning 16 data groupsin one sub-frame using the above-described pattern (or rule). In otherwords, each data group is serially assigned to 16 slots corresponding tothe following numbers: 0, 8, 4, 12, 1, 9, 5, 13, 2, 10, 6, 14, 3, 11, 7,and 15. Equation 1 below shows the above-described rule (or pattern) forassigning data groups in a sub-frame.

j=(4i+0) mod 16

0=0 if i<4,

0=2 else if i<8,

Herein,

0=1 else if i<12,

0=3 else.

Herein, j indicates the slot number within a sub-frame. The value of jmay range from 0 to 15 (i.e., 0≦j≦15). Also, variable i indicates thedata group number. The value of i may range from 0 to 15 (i.e., 0≦j≦15).

In the present invention, a collection of data groups included in a MHframe will be referred to as a “parade”. Based upon the RS frame mode,the parade transmits data of at least one specific RS frame.

The mobile service data within one RS frame may be assigned either toall of regions A/B/C/D within the corresponding data group, or to atleast one of regions A/B/C/D. In the embodiment of the presentinvention, the mobile service data within one RS frame may be assignedeither to all of regions A/B/C/D, or to at least one of regions A/B andregions C/D. If the mobile service data are assigned to the latter case(i.e., one of regions A/B and regions C/D), the RS frame being assignedto regions A/B and the RS frame being assigned to regions C/D within thecorresponding data group are different from one another.

According to the embodiment of the present invention, the RS frame beingassigned to regions A/B within the corresponding data group will bereferred to as a “primary RS frame”, and the RS frame being assigned toregions C/D within the corresponding data group will be referred to as a“secondary RS frame”, for simplicity. Also, the primary RS frame and thesecondary RS frame form (or configure) one parade. More specifically,when the mobile service data within one RS frame are assigned either toall of regions A/B/C/D within the corresponding data group, one paradetransmits one RS frame. Conversely, when the mobile service data withinone RS frame are assigned either to at least one of regions A/B andregions C/D, one parade may transmit up to 2 RS frames. Morespecifically, the RS frame mode indicates whether a parade transmits oneRS frame, or whether the parade transmits two RS frames. Such RS framemode is transmitted as the above-described TPC data. Table 1 below showsan example of the RS frame mode.

TABLE 1 RS frame mode (2 bits) Description 00 There is only one primaryRS frame for all group regions 01 There are two separate RS frames.Primary RS frame for group regions A and B Secondary RS frame for groupregions C and D 10 Reserved 11 Reserved

Table 1 illustrates an example of allocating 2 bits in order to indicatethe RS frame mode. For example, referring to Table 1, when the RS framemode value is equal to ‘00’, this indicates that one parade transmitsone RS frame. And, when the RS frame mode value is equal to ‘01’, thisindicates that one parade transmits two RS frames, i.e., the primary RSframe and the secondary RS frame.

More specifically, when the RS frame mode value is equal to ‘01’, dataof the primary RS frame for regions A/B are assigned and transmitted toregions A/B of the corresponding data group. Similarly, data of thesecondary RS frame for regions C/D are assigned and transmitted toregions C/D of the corresponding data group.

As described in the assignment of data groups, the parades are alsoassigned to be spaced as far apart from one another as possible withinthe sub-frame. Thus, the system can be capable of responding promptlyand effectively to any burst error that may occur within a sub-frame.Furthermore, the method of assigning parades may be identically appliedto all MH frames or differently applied to each MH frame.

According to the embodiment of the present invention, the parades may beassigned differently for each MH frame and identically for allsub-frames within an MH frame. More specifically, the MH frame structuremay vary by MH frame units. Thus, an ensemble rate may be adjusted on amore frequent and flexible basis.

FIG. 9 illustrates an example of multiple data groups of a single paradebeing assigned (or allocated) to an MH frame. More specifically, FIG. 9illustrates an example of a plurality of data groups included in asingle parade, wherein the number of data groups included in a sub-frameis equal to ‘3’, being allocated to an MH frame.

Referring to FIG. 9, 3 data groups are sequentially assigned to asub-frame at a cycle period of 4 slots. Accordingly, when this processis equally performed in the 5 sub-frames included in the correspondingMH frame, 15 data groups are assigned to a single MH frame. Herein, the15 data groups correspond to data groups included in a parade.Therefore, since one sub-frame is configured of 4 VSB frame, and since 3data groups are included in a sub-frame, the data group of thecorresponding parade is not assigned to one of the 4 VSB frames within asub-frame.

For example, when it is assumed that one parade transmits one RS frame,and that a RS frame encoder (not shown) included in the transmittingsystem performs RS-encoding on the corresponding RS frame, therebyadding 24 bytes of parity data to the corresponding RS frame andtransmitting the processed RS frame, the parity data occupyapproximately 11.37% (=24/(187+24)×100) of the total code word length.Meanwhile, when one sub-frame includes 3 data groups, and when the datagroups included in the parade are assigned, as shown in FIG. 9, a totalof 15 data groups form an RS frame. Accordingly, even when an erroroccurs in an entire data group due to a burst noise within a channel,the percentile is merely 6.67% (=1/15×100). Therefore, the receivingsystem may correct all errors by performing an erasure RS decodingprocess. More specifically, when the erasure RS decoding is performed, anumber of channel errors corresponding to the number of RS parity bytesmay be corrected. By doing so, the receiving system may correct theerror of at least one data group within one parade. Thus, the minimumburst noise length correctable by a RS frame is over 1 VSB frame.

Meanwhile, when data groups of a parade are assigned as shown in FIG. 9,either main service data may be assigned between each data group, ordata groups corresponding to different parades may be assigned betweeneach data group. More specifically, data groups corresponding tomultiple parades may be assigned to one MH frame.

Basically, the method of assigning data groups corresponding to multipleparades is very similar to the method of assigning data groupscorresponding to a single parade. In other words, data groups includedin other parades that are to be assigned to an MH frame are alsorespectively assigned according to a cycle period of 4 slots.

At this point, data groups of a different parade may be sequentiallyassigned to the respective slots in a circular method. Herein, the datagroups are assigned to slots starting from the ones to which data groupsof the previous parade have not yet been assigned.

For example, when it is assumed that data groups corresponding to aparade are assigned as shown in FIG. 9, data groups corresponding to thenext parade may be assigned to a sub-frame starting either from the12^(th) slot of a sub-frame. However, this is merely exemplary. Inanother example, the data groups of the next parade may also besequentially assigned to a different slot within a sub-frame at a cycleperiod of 4 slots starting from the 3^(rd) slot.

FIG. 10 illustrates an example of transmitting 3 parades (Parade #0,Parade #1, and Parade #2) to an MH frame. More specifically, FIG. 10illustrates an example of transmitting parades included in one of 5sub-frames, wherein the 5 sub-frames configure one MH frame.

When the 1^(st) parade (Parade #0) includes 3 data groups for eachsub-frame, the positions of each data groups within the sub-frames maybe obtained by substituting values ‘0’ to ‘2’ for i in Equation 1. Morespecifically, the data groups of the 1^(st) parade (Parade #0) aresequentially assigned to the 1^(st), 5^(th), and 9^(th) slots (Slot #0,Slot #4, and Slot #8) within the sub-frame.

Also, when the 2nd parade includes 2 data groups for each sub-frame, thepositions of each data groups within the sub-frames may be obtained bysubstituting values ‘3’ and ‘4’ for i in Equation 1. More specifically,the data groups of the 2^(nd) parade (Parade #1) are sequentiallyassigned to the 2^(nd) and 12^(th) slots (Slot #3 and Slot #11) withinthe sub-frame.

Finally, when the 3^(rd) parade includes 2 data groups for eachsub-frame, the positions of each data groups within the sub-frames maybe obtained by substituting values ‘5’ and ‘6’ for i in Equation 1. Morespecifically, the data groups of the 3^(rd) parade (Parade #2) aresequentially assigned to the 7^(th) and 11^(th) slots (Slot #6 and Slot#10) within the sub-frame.

As described above, data groups of multiple parades may be assigned to asingle MH frame, and, in each sub-frame, the data groups are seriallyallocated to a group space having 4 slots from left to right.

Therefore, a number of groups of one parade per sub-frame (NoG) maycorrespond to any one integer from ‘1’ to ‘8’. Herein, since one MHframe includes 5 sub-frames, the total number of data groups within aparade that can be allocated to an MH frame may correspond to any onemultiple of ‘5’ ranging from ‘5’ to ‘40’.

FIG. 11 illustrates an example of expanding the assignment process of 3parades, shown in FIGS. 10, to 5 sub-frames within an MH frame.

FIG. 12 illustrates a data transmission structure according to anembodiment of the present invention, wherein signaling data are includedin a data group so as to be transmitted.

As described above, an MH frame is divided into 5 sub-frames. Datagroups corresponding to a plurality of parades co-exist in eachsub-frame. Herein, the data groups corresponding to each parade aregrouped by MH frame units, thereby configuring a single parade. The datastructure shown in FIG. 12 includes 3 parades, one ESG dedicated channel(EDC) parade (i.e., parade with NoG=1), and 2 service parades (i.e.,parade with NoG=4 and parade with NoG=3). Also, a predetermined portionof each data group (i.e., 37 bytes/data group) is used for delivering(or sending) FIC information associated with mobile service data,wherein the FIC information is separately encoded from the RS-encodingprocess. The FIC region assigned to each data group consists of one FICsegments. Herein, each segment is interleaved by MH sub-frame units,thereby configuring an FIC body, which corresponds to a completed FICtransmission structure. However, whenever required, each segment may beinterleaved by MH frame units and not by MH sub-frame units, therebybeing completed in MH frame units.

Meanwhile, the concept of an MH ensemble is applied in the embodiment ofthe present invention, thereby defining a collection (or group) ofservices. Each MH ensemble carries the same QoS and is coded with thesame FEC code. Also, each MH ensemble has the same unique identifier(i.e., ensemble ID) and corresponds to consecutiveRS frames.

As shown in FIG. 12, the FIC segment corresponding to each data groupdescribed service information of an MH ensemble to which thecorresponding data group belongs. When FIC segments within a sub-frameare grouped and deinterleved, all service information of a physicalchannel through which the corresponding FICs are transmitted may beobtained. Therefore, the receiving system may be able to acquire thechannel information of the corresponding physical channel, after beingprocessed with physical channel tuning, during a sub-frame period.

Furthermore, FIG. 12 illustrates a structure further including aseparate EDC parade apart from the service parade and wherein electronicservice guide (ESG) data are transmitted in the 1^(st) slot of eachsub-frame.

If the digital broadcasting reception system recognizes a frame startpoint or a frame end point of the MH frame (or the MH subframe), thenthe digital broadcasting reception system can set the reference timeinformation to the system time clock at the frame start point or theframe end point. The reference time information can be the network timeprotocol (NTP) timestamp. The detailed description for the referencetime information will be disclosed by being referred to FIGS. 25 to 29.

Hierarchical Signaling Structure

FIG. 13 illustrates a hierarchical signaling structure according to anembodiment of the present invention. As shown in FIG. 13, the mobilebroadcasting techonology according to the embodiment of the presentinvention adopts a signaling method using FIC and SMT. In thedescription of the present invention, the signaling structure will bereferred to as a hierarchical signaling structure.

Hereinafter, a detailed description on how the receiving system accessesa virtual channel via FIC and SMT will now be given with reference toFIG. 13.

The FIC body defined in an MH transport (M1) identifies the physicallocation of each the data stream for each virtual channel and providesvery high level descriptions of each virtual channel.

Being MH ensemble level signaling information, the service map table(SMT) provides MH ensemble level signaling information. The SMT providesthe IP access information of each virtual channel belonging to therespective MH ensemble within which the SMT is carried. The SMT alsoprovides all IP stream component level information required for thevirtual channel service acquisition.

Referring to FIG. 13, each MH ensemble (i.e., Ensemble 0, Ensemble 1, .. . , Ensemble K) includes a stream information on each associated (orcorresponding) virtual channel (e.g., virtual channel 0 IP stream,virtual channel 1 IP stream, and virtual channel 2 IP stream). Forexample, Ensemble 0 includes virtual channel 0 IP stream and virtualchannel 1 IP stream. And, each MH ensemble includes diverse informationon the associated virtual channel (i.e., Virtual Channel 0 Table Entry,Virtual Channel 0 Access Info, Virtual Channel 1 Table Entry, VirtualChannel 1 Access Info, Virtual Channel 2 Table Entry, Virtual Channel 2Access Info, Virtual Channel N Table Entry, Virtual Channel N AccessInfo, and so on).

The FIC body payload includes information on MH ensembles (e.g.,ensemble_id field, and referred to as “ensemble location” in FIG. 13)and information on a virtual channel associated with the correspondingMH ensemble (e.g., when such information corresponds to amajor_channel_num field and a minor_channel_num field, the informationis expressed as Virtual Channel 0, Virtual Channel 1, Virtual Channel Nin FIG. 13).

The application of the signaling structure in the receiving system willnow be described in detail.

When a user selects a channel he or she wishes to view (hereinafter, theuser-selected channel will be referred to as “channel θ” forsimplicity), the receiving system first parses the received FIC. Then,the receiving system acquires information on an MH ensemble (i.e.,ensemble location), which is associated with the virtual channelcorresponding to channel θ (hereinafter, the corresponding MH ensemblewill be referred to as “MH ensemble θ” for simplicity). By acquiringslots only corresponding to the MH ensemble θ using the time-slicingmethod, the receiving system configures ensemble θ. The ensemble θconfigured as described above, includes an SMT on the associated virtualchannels (including channel θ) and IP streams on the correspondingvirtual channels. Therefore, the receiving system uses the SMT includedin the MH ensemble θ in order to acquire various information on channelθ (e.g., Virtual Channel θ Table Entry) and stream access information onchannel θ (e.g., Virtual Channel 0 Access Info). The receiving systemuses the stream access information on channel 0 to receive only theassociated IP streams, thereby providing channel 0 services to the user.

Fast Information Channel (FIC)

The digital broadcast receiving system according to the presentinvention adopts the fast information channel (FIC) for a faster accessto a service that is currently being broadcasted.

More specifically, the FIC handler 215 of FIG. 1 parses the FIC body,which corresponds to an FIC transmission structure, and outputs theparsed result to the physical adaptation control signal handler 216.

FIG. 14 illustrates an exemplary FIC body format according to anembodiment of the present invention. According to the embodiment of thepresent invention, the FIC format consists of an FIC body header and anFIC body payload.

Meanwhile, according to the embodiment of the present invention, dataare transmitted through the FIC body header and the FIC body payload inFIC segment units. Each FIC segment has the size of 37 bytes, and eachFIC segment consists of a 2-byte FIC segment header and a 35-byte FICsegment payload. More specifically, an FIC body configured of an FICbody header and an FIC body payload, is segmented in units of 35 databytes, which are then carried in at least one FIC segment within the FICsegment payload, so as to be transmitted.

In the description of the present invention, an example of inserting oneFIC segment in one data group, which is then transmitted, will be given.In this case, the receiving system receives a slot corresponding to eachdata group by using a time-slicing method.

The signaling decoder 190 included in the receiving system shown in FIG.1 collects each FIC segment inserted in each data group. Then, thesignaling decoder 190 uses the collected FIC segments to created asingle FIC body. Thereafter, the signaling decoder 190 performs adecoding process on the FIC body payload of the created FIC body, sothat the decoded FIC body payload corresponds to an encoded result of asignaling encoder (not shown) included in the transmitting system.Subsequently, the decoded FIC body payload is outputted to the FIChandler 215. The FIC handler 215 parses the FIC data included in the FICbody payload, and then outputs the parsed FIC data to the physicaladaptation control signal handler 216. The physical adaptation controlsignal handler 216 uses the inputted FIC data to perform processesassociated with MH ensembles, virtual channels, SMTs, and so on.

According to an embodiment of the present invention, when an FIC body issegmented, and when the size of the last segmented portion is smallerthan 35 data bytes, it is assumed that the lacking number of data bytesin the FIC segment payload is completed with by adding the same numberof stuffing bytes therein, so that the size of the last FIC segment canbe equal to 35 data bytes.

However, it is apparent that the above-described data byte values (i.e.,37 bytes for the FIC segment, 2 bytes for the FIC segment header, and 35bytes for the FIC segment payload) are merely exemplary, and will,therefore, not limit the scope of the present invention.

FIG. 15 illustrates an exemplary bit stream syntax structure withrespect to an FIC segment according to an embodiment of the presentinvention.

Herein, the FIC segment signifies a unit used for transmitting the FICdata. The FIC segment consists of an FIC segment header and an FICsegment payload. Referring to FIG. 15, the FIC segment payloadcorresponds to the portion starting from the ‘for’ loop statement.Meanwhile, the FIC segment header may include a FIC_type field, an errorindicator field, an FIC_seg_number field, and an FIC_last_seg_numberfield. A detailed description of each field will now be given.

The FIC_type field is a 2-bit field indicating the type of thecorresponding FIC.

The error_indicator field is a 1-bit field, which indicates whether ornot an error has occurred within the FIC segment during datatransmission. If an error has occurred, the value of the error indicatorfield is set to ‘1’. More specifically, when an error that has failed tobe recovered still remains during the configuration process of the FICsegment, the error indicator field value is set to ‘1’. The errorindicator field enables the receiving system to recognize the presenceof an error within the FIC data.

The FIC_seg_number field is a 4-bit field. Herein, when a single FICbody is divided into a plurality of FIC segments and transmitted, theFIC_seg_number field indicates the number of the corresponding FICsegment.

Finally, the FIC_last_seg_number field is also a 4-bit field. TheFIC_last_seg_number field indicates the number of the last FIC segmentwithin the corresponding FIC body.

FIG. 16 illustrates an exemplary bit stream syntax structure withrespect to a payload of an FIC segment according to the presentinvention, when an FIC type field value is equal to ‘0’.

According to the embodiment of the present invention, the payload of theFIC segment is divided into 3 different regions. A first region of theFIC segment payload exists only when the FIC_seg_number field value isequal to ‘0’. Herein, the first region may include acurrent_next_indicator field, an ESG_version field, and atransport_stream_id field. However, depending upon the embodiment of thepresent invention, it may be assumed that each of the 3 fields existsregardless of the FIC_seg_number field.

The current_next_indicator field is a 1-bit field. Thecurrent_next_indicator field acts as an indicator identifying whetherthe corresponding FIC data carry MH ensemble configuration informationof an MH frame including the current FIC segment, or whether thecorresponding FIC data carry MH ensemble configuration information of anext MH frame.

The ESG_version field is a 5-bit field indicating ESG versioninformation. Herein, by providing version information on the serviceguide providing channel of the corresponding ESG, the ESG_version fieldenables the receiving system to notify whether or not the correspondingESG has been updated.

Finally, the transport_stream_id field is a 16-bit field acting as aunique identifier of a broadcast stream through which the correspondingFIC segment is being transmitted.

A second region of the FIC segment payload corresponds to an ensembleloop region, which includes an ensemble_id field, an SI_version field,and a num_channel field.

More specifically, the ensemble_id field is an 8-bit field indicatingidentifiers of an MH ensemble through which MH services are transmitted.The MH services will be described in more detail in a later process.Herein, the ensemble_id field binds the MH services and the MH ensemble.

The SI_version field is a 4-bit field indicating version information ofSI data included in the corresponding ensemble, which is beingtransmitted within the RS frame.

Finally, the num_channel field is an 8-bit field indicating the numberof virtual channel being transmitted via the corresponding ensemble.

A third region of the FIC segment payload a channel loop region, whichincludes a channel_type field, a channel_activity field, a CA_indicatorfield, a stand_alone_service_indicator field, a major_channel_num field,and a minor_channel_num field.

The channel_type field is a 5-bit field indicating a service type of thecorresponding virtual channel. For example, the channel_type field mayindicates an audio/video channel, an audio/video and data channel, anaudio-only channel, a data-only channel, a file download channel, an ESGdelivery channel, a notification channel, and so on.

The channel_activity field is a 2-bit field indicating activityinformation of the corresponding virtual channel. More specifically, thechannel_activity field may indicate whether the current virtual channelis providing the current service.

The CA_indicator field is a 1-bit field indicating whether or not aconditional access (CA) is applied to the current virtual channel.

The stand_alone_service_indicator field is also a 1-bit field, whichindicates whether the service of the corresponding virtual channelcorresponds to a stand alone service.

The major_channel_num field is an 8-bit field indicating a major channelnumber of the corresponding virtual channel.

Finally, the minor_channel_num field is also an 8-bit field indicating aminor channel number of the corresponding virtual channel.

Service Table Map

FIG. 17 illustrates an exemplary bit stream syntax structure of aservice map table (hereinafter referred to as “SMT”) according to thepresent invention.

According to the embodiment of the present invention, the SMT isconfigured in an MPEG-2 private section format. However, this will notlimit the scope and spirit of the present invention. The SMT accordingto the embodiment of the present invention includes descriptioninformation for each virtual channel within a single MH ensemble. And,additional information may further be included in each descriptor area.

Herein, the SMT according to the embodiment of the present inventionincludes at least one field and is transmitted from the transmittingsystem to the receiving system.

As described in FIG. 3, the SMT section may be transmitted by beingincluded in the MH TP within the RS frame. In this case, each of the RSframe decoders 170 and 180, shown in FIG. 1, decodes the inputted RSframe, respectively. Then, each of the decoded RS frames is outputted tothe respective RS frame handler 211 and 212. Thereafter, each RS framehandler 211 and 212 identifies the inputted RS frame by row units, so asto create an MH TP, thereby outputting the created MH TP to the MH TPhandler 213. When it is determined that the corresponding MH TP includesan SMT section based upon the header in each of the inputted MH TP, theMH TP handler 213 parses the corresponding SMT section, so as to outputthe SI data within the parsed SMT section to the physical adaptationcontrol signal handler 216. However, this is limited to when the SMT isnot encapsulated to IP datagrams.

Meanwhile, when the SMT is not encapsulated to IP datagrams, and when itis determined that the corresponding MH TP includes an SMT section basedupon the header in each of the inputted MH TP, the MH TP handler 213outputs the SMT section to the IP network stack 220. Accordingly, the IPnetwork stack 220 performs IP and UDP processes on the inputted SMTsection and, then, outputs the processed SMT section to the SI handler240. The SI handler 240 parses the inputted SMT section and controls thesystem so that the parsed SI data can be stored in the storage unit 290.

The following corresponds to example of the fields that may betransmitted through the SMT.

The table_id field corresponds to an 8-bit unsigned integer number,which indicates the type of table section. The table_(—id) field allowsthe corresponding table to be defined as the service map table (SMT).

The ensemble_id field is an 8-bit unsigned integer field, whichcorresponds to an ID value associated to the corresponding MH ensemble.Herein, the ensemble_id field may be assigned with a value ranging fromrange ‘0x00’ to ‘0x3F’. It is preferable that the value of theensemble_id field is derived from the parade_id of the TPC data, whichis carried from the baseband processor of MH physical layer subsystem.When the corresponding MH ensemble is transmitted through (or carriedover) the primary RS frame, a value of ‘0’ may be used for the mostsignificant bit (MSB), and the remaining 7 bits are used as theparade_id value of the associated MH parade (i.e., for the leastsignificant 7 bits). Alternatively, when the corresponding MH ensembleis transmitted through (or carried over) the secondary RS frame, a valueof ‘1’ may be used for the most significant bit (MSB).

The num_channels field is an 8-bit field, which specifies the number ofvirtual channels in the corresponding SMT section.

Meanwhile, the SMT according to the embodiment of the present inventionprovides information on a plurality of virtual channels using the ‘for’loop statement.

The major_channel_num field corresponds to an 8-bit field, whichrepresents the major channel number associated with the correspondingvirtual channel. Herein, the major_channel_num field may be assignedwith a value ranging from ‘0x00’ to ‘0xFF’.

The minor_channel_num field corresponds to an 8-bit field, whichrepresents the minor channel number associated with the correspondingvirtual channel. Herein, the minor_channel_num field may be assignedwith a value ranging from ‘0x00’ to ‘0xFF’.

The short_channel_name field indicates the short name of the virtualchannel.

The service_id field is a 16-bit unsigned integer number (or value),which identifies the virtual channel service.

The service_type field is a 6-bit enumerated type field, whichdesignates the type of service carried in the corresponding virtualchannel as defined in Table 2 below.

TABLE 2 0x00 [Reserved] 0x01 MH_digital_television field: the virtualchannel carries television programming (audio, video and optionalassociated data) conforming to ATSC standards. 0x02 MH_audio field: thevirtual channel carries audio programming (audio service and optionalassociated data) conforming to ATSC standards. 0x03 MH_data_only_servicefield: the virtual channel carries a data service conforming to ATSCstandards, but no video or audio component. 0x04 to 0xFF [Reserved forfuture ATSC usage]

The virtual_channel_activity field is a 2-bit enumerated fieldidentifying the activity status of the corresponding virtual channel.When the most significant bit (MSB) of the virtual_channel_activityfield is ‘1’, the virtual channel is active, and when the mostsignificant bit (MSB) of the virtual_channel_activity field is ‘0’, thevirtual channel is inactive. Also, when the least significant bit (LSB)of the virtual_channel_activity field is ‘1’, the virtual channel ishidden (when set to 1), and when the least significant bit (LSB) of thevirtual_channel_activity field is ‘0’, the virtual channel is nothidden.

The num_components field is a 5-bit field, which specifies the number ofIP stream components in the corresponding virtual channel.

The IP_version_flag field corresponds to a 1-bit indicator. Morespecifically, when the value of the IP_version_flag field is set to ‘1’,this indicates that a source_IP_address field, avirtual_channel_target_IP address field, and a component_target_IPaddress field are IPv6 addresses. Alternatively, when the value of theIP_version_flag field is set to ‘0’, this indicates that thesource_IP_address field, the virtual_channel_target_IP address field,and the component_target_IP_address field are IPv4.

The source_IP_address_flag field is a 1-bit Boolean flag, whichindicates, when set, that a source IP address of the correspondingvirtual channel exist for a specific multicast source.

The virtual_channel_target_IP_address_flag field is a 1-bit Booleanflag, which indicates, when set, that the corresponding IP streamcomponent is delivered through IP datagrams with target IP addressesdifferent from the virtual_channel_target_IP_address. Therefore, whenthe flag is set, the receiving system (or receiver) uses thecomponent_target_IP_address as the target_IP_address in order to accessthe corresponding IP stream component. Accordingly, the receiving system(or receiver) may ignore the virtual_channel_target_IP_address fieldincluded in the num_channels loop.

The source IP address field corresponds to a 32-bit or 128-bit field.Herein, the source_IP_address field will be significant (or present),when the value of the source_IP_address_flag field is set to ‘1’.However, when the value of the source_IP_address_flag field is set to‘0’, the source_IP_address field will become insignificant (or absent).More specifically, when the source_IP_address_flag field value is set to‘1’, and when the IP_version_flag field value is set to ‘0’, thesource_IP_address field indicates a 32-bit IPv4 address, which shows thesource of the corresponding virtual channel. Alternatively, when theIP_version_flag field value is set to ‘1’, the source_IP_address fieldindicates a 128-bit IPv6 address, which shows the source of thecorresponding virtual channel.

The virtual_channel_target_IP_address field also corresponds to a 32-bitor 128-bit field. Herein, the virtual_channel_target_IP_address fieldwill be significant (or present), when the value of thevirtual_channel_target_IP_address_flag field is set to ‘1’. However,when the value of the virtual_channel_target_IP_address_flag field isset to ‘0’, the virtual_channel_target_IP_address_field will becomeinsignificant (or absent). More specifically, when thevirtual_channel_target_IP_address_flag field value is set to ‘1’, andwhen the IP_version_flag field value is set to ‘0’, thevirtual_channel_target_IP_address field indicates a 32-bit target IPv4address associated to the corresponding virtual channel. Alternatively,when the virtual_channel_target_IP_address_flag field value is set to‘1’, and when the IP_version_flag field value is set to ‘1’, thevirtual_channel_target_IP address field indicates a 64-bit target IPv6address associated to the corresponding virtual channel. If thevirtual_channel_target_IP_address field is insignificant (or absent),the component_target_IP_address field within the num_channels loopshould become significant (or present). And, in order to enable thereceiving system to access the IP stream component, thecomponent_target_IP_address field should be used.

Meanwhile, the SMT according to the embodiment of the present inventionuses a ‘for’ loop statement in order to provide information on aplurality of components.

Herein, the RTP_payload_type field, which is assigned with 7 bits,identifies the encoding format of the component based upon Table 3 shownbelow. When the IP stream component is not encapsulated to RTP, theRTP_payload_type field shall be ignored (or deprecated).

Table 3 below shows an example of an RTP payload type.

TABLE 3 RTP_payload_type Meaning 35 AVC video 36 MH audio 37 to 72[Reserved for future ATSC use]

The component_target_IP_address_flag field is a 1-bit Boolean flag,which indicates, when set, that the corresponding IP stream component isdelivered through IP datagrams with target IP addresses different fromthe virtual_channel_target_IP_address. Furthermore, when thecomponent_target_IP_address_flag is set, the receiving system (orreceiver) uses the component_target_IP_address field as the target IPaddress for accessing the corresponding IP stream component.Accordingly, the receiving system (or receiver) will ignore thevirtual_channel_target_IP_address field included in the num_channelsloop.

The component_target_IP_address field corresponds to a 32-bit or 128-bitfield. Herein, when the value of the IP_version_flag field is set to‘0’, the component_target_IP_address field indicates a 32-bit targetIPv4 address associated to the corresponding IP stream component. And,when the value of the IP_version_flag field is set to ‘1’, thecomponent_target_IP_address field indicates a 128-bit target IPv6address associated to the corresponding IP stream component.

The port_num_count field is a 6-bit field, which indicates the number ofUDP ports associated with the corresponding IP stream component. Atarget UDP port number value starts from the target_UDP_port_num fieldvalue and increases (or is incremented) by 1. For the RTP stream, thetarget UDP port number should start from the target_UDP_port_num fieldvalue and shall increase (or be incremented) by 2. This is toincorporate RTCP streams associated with the RTP streams.

The target_UDP_port_num field is a 16-bit unsigned integer field, whichrepresents the target UDP port number for the corresponding IP streamcomponent. When used for RTP streams, the value of thetarget_UDP_port_num field shall correspond to an even number. And, thenext higher value shall represent the target UDP port number of theassociated RTCP stream.

The component_level_descriptor( ) represents zero or more descriptorsproviding additional information on the corresponding IP streamcomponent.

The virtual_channel_level_descriptor( ) represents zero or moredescriptors providing additional information for the correspondingvirtual channel.

The ensemble_level_descriptor( ) represents zero or more descriptorsproviding additional information for the MH ensemble, which is describedby the corresponding SMT.

FIG. 18 illustrates an exemplary bit stream syntax structure of an MHaudio descriptor according to the present invention. When at least oneaudio service is present as a component of the current event, theMH_audio_descriptor( ) shall be used as a component_level_descriptor ofthe SMT. The MH_audio_descriptor( ) may be capable of informing thesystem of the audio language type and stereo mode status. If there is noaudio service associated with the current event, then it is preferablethat the MH_audio_descriptor( ) is considered to be insignificant (orabsent) for the current event. Each field shown in the bit stream syntaxof FIG. 18 will now be described in detail.

The descriptor_tag field is an 8-bit unsigned integer having a TBDvalue, which indicates that the corresponding descriptor is theMH_audio_descriptor( ). The descriptor_length field is also an 8-bitunsigned integer, which indicates the length (in bytes) of the portionimmediately following the descriptor_length field up to the end of theMH_audio_descriptor( ). The channel configuration field corresponds toan 8-bit field indicating the number and configuration of audiochannels. The values ranging from ‘1’ to ‘6’ respectively indicate thethe number and configuration of audio channels as given for “Default bitstream index number” in Table 42 of ISO/IEC 13818-7:2006. All othervalues indicate that the number and configuration of audio channels areundefined.

The sample_rate_code field is a 3-bit field, which indicates the samplerate of the encoded audio data. Herein, the indication may correspond toone specific sample rate, or may correspond to a set of values thatinclude the sample rate of the encoded audio data as defined in TableA3.3 of ATSC A/52B. The bit_rate_code field corresponds to a 6-bitfield. Herein, among the 6 bits, the lower 5 bits indicate a nominal bitrate. More specifically, when the most significant bit (MSB) is ‘0’, thecorresponding bit rate is exact. On the other hand, when the mostsignificant bit (MSB) is ‘0’, the bit rate corresponds to an upper limitas defined in Table A3.4 of ATSC A/53B. The ISO_639_language_code fieldis a 24-bit (i.e., 3-byte) field indicating the language used for theaudio stream component, in conformance with ISO 639.2/B [x]. When aspecific language is not present in the corresponding audio streamcomponent, the value of each byte will be set to ‘0x00’.

FIG. 19 illustrates an exemplary bit stream syntax structure of an MHRTP payload type descriptor according to the present invention.

The MH_RTP_payload_type_descriptor( ) specifies the RTP payload type.Yet, the MH_RTP_payload_type_descriptor( ) exists only when the dynamicvalue of the RTP_payload_type field within the num_components loop ofthe SMT is in the range of ‘96’ to ‘127’. TheMH_RTP_payload_type_descriptor( ) is used as acomponent_level_descriptor of the SMT.

The MH_RTP_payload_type_descriptor translates (or matches) a dynamicRTP_payload_type field value into (or with) a MIME type. Accordingly,the receiving system (or receiver) may collect (or gather) the encodingformat of the IP stream component, which is encapsulated in RTP.

The fields included in the MH_RTP_payload_type_descriptor( ) will now bedescribed in detail.

The descriptor_tag field corresponds to an 8-bit unsigned integer havingthe value TBD, which identifies the current descriptor as theMH_RTP_payload_type_descriptor( ).

The descriptor_length field also corresponds to an 8-bit unsignedinteger, which indicates the length (in bytes) of the portionimmediately following the descriptor length field up to the end of theMH_RTP_payload_type_descriptor( ).

The RTP_payload_type field corresponds to a 7-bit field, whichidentifies the encoding format of the IP stream component. Herein, thedynamic value of the RTP_payload_type field is in the range of ‘96’ to‘127’.

The MIME_type_length field specifies the length (in bytes) of theMIME_type field.

The MIME_type field indicates the MIME type corresponding to theencoding format of the IP stream component, which is described by theMH_RTP_payload_type_descriptor( ).

FIG. 20 illustrates an exemplary bit stream syntax structure of an MHcurrent event descriptor according to the present invention.

The MH_current_event_descriptor( )shall be used as thevirtual_channel_level_descriptor( ) within the SMT. Herein, theMH_current_event_descriptor( ) provides basic information on the currentevent (e.g., the start time, duration, and title of the current event,etc.), which is transmitted via the respective virtual channel.

The fields included in the MH_current_event_descriptor( ) will now bedescribed in detail.

The descriptor_tag field corresponds to an 8-bit unsigned integer havingthe value TBD, which identifies the current descriptor as theMH_current_event_descriptor( ).

The descriptor_length field also corresponds to an 8-bit unsignedinteger, which indicates the length (in bytes) of the portionimmediately following the descriptor_length field up to the end of theMH_current_event_descriptor( ).

The current_event_start_time field corresponds to a 32-bit unsignedinteger quantity. The current_event_start_time field represents thestart time of the current event and, more specifically, as the number ofGPS seconds since 00:00:00 UTC, Jan. 6, 1980.

The current_event_duration field corresponds to a 24-bit field. Herein,the current_event_duration field indicates the duration of the currentevent in hours, minutes, and seconds (wherein the format is in 6 digits,4-bit BCD=24 bits).

The title_length field specifies the length (in bytes) of the title_textfield. Herein, the value ‘0’ indicates that there are no titles existingfor the corresponding event.

The title_text field indicates the title of the corresponding event inevent title in the format of a multiple string structure as defined inATSC A/65C [x].

FIG. 21 illustrates an exemplary bit stream syntax structure of an MHnext event descriptor according to the present invention.

The optional MH_next_event_descriptor( ) shall be used as thevirtual_channel_level_descriptor( ) within the SMT. Herein, theMH_next_event_descriptor( ) provides basic information on the next event(e.g., the start time, duration, and title of the next event, etc.),which is transmitted via the respective virtual channel. The fieldsincluded in the

MH_next_event_descriptor( ) will now be described in detail.

The descriptor_tag field corresponds to an 8-bit unsigned integer havingthe value TBD, which identifies the current descriptor as theMH_next_event_descriptor( ).

The descriptor length field also corresponds to an 8-bit unsignedinteger, which indicates the length (in bytes) of the portionimmediately following the descriptor_length field up to the end of theMH_next_event_descriptor( ).

The next_event_start_time field corresponds to a 32-bit unsigned integerquantity. The next_event_start_time field represents the start time ofthe next event and, more specifically, as the number of GPS secondssince 00:00:00 UTC, Jan. 6, 1980.

The next_event_duration field corresponds to a 24-bit field. Herein, thenext_event_duration field indicates the duration of the next event inhours, minutes, and seconds (wherein the format is in 6 digits, 4-bitBCD=24 bits).

The title_length field specifies the length (in bytes) of the title_textfield. Herein, the value ‘0’ indicates that there are no titles existingfor the corresponding event.

The title_text field indicates the title of the corresponding event inevent title in the format of a multiple string structure as defined inATSC A/65C [x].

FIG. 22 illustrates an exemplary bit stream syntax structure of an MHsystem time descriptor according to the present invention.

The MH_system_time_descriptor( ) shall be used as theensemble_level_descriptor( ) within the SMT. Herein, theMH_system_time_descriptor( ) provides information on current time anddate.

The MH_system_time_descriptor( ) also provides information on the timezone in which the transmitting system (or transmitter) transmitting thecorresponding broadcast stream is located, while taking intoconsideration the mobile/portable characteristics of the MH servicedata. The fields included in the MH_system_time_descriptor( ) will nowbe described in detail.

The descriptor_tag field corresponds to an 8-bit unsigned integer havingthe value TBD, which identifies the current descriptor as theMH_system_time_descriptor( ).

The descriptor_length field also corresponds to an 8-bit unsignedinteger, which indicates the length (in bytes) of the portionimmediately following the descriptor_length field up to the end of theMH_system_time_descriptor( ).

The system_time field corresponds to a 32-bit unsigned integer quantity.The system_time field represents the current system time and, morespecifically, as the number of GPS seconds since 00:00:00 UTC, Jan. 6,1980.

The GPS_UTC_offset field corresponds to an 8-bit unsigned integer, whichdefines the current offset in whole seconds between GPS and UTC timestandards. In order to convert GPS time to UTC time, the GPS_UTC_offsetis subtracted from GPS time. Whenever the International Bureau ofWeights and Measures decides that the current offset is too far inerror, an additional leap second may be added (or subtracted).Accordingly, the GPS_UTC_offset field value will reflect the change.

The time_zone_offset_polarity field is a 1-bit field, which indicateswhether the time of the time zone, in which the broadcast station islocated, exceeds (or leads or is faster) or falls behind (or lags or isslower) than the UTC time. When the value of thetime_zone_offset_polarity field is equal to ‘0’, this indicates that thetime on the current time zone exceeds the UTC time. Therefore, thetime_zone_offset_polarity field value is added to the UTC time value.Conversely, when the value of the time_zone_offset_polarity field isequal to ‘1’, this indicates that the time on the current time zonefalls behind the UTC time. Therefore, the time_zone_offset_polarityfield value is subtracted from the UTC time value.

The time_zone_offset field is a 31-bit unsigned integer quantity. Morespecifically, the time_zone_offset field represents, in GPS seconds, thetime offset of the time zone in which the broadcast station is located,when compared to the UTC time.

The daylight_savings field corresponds to a 16-bit field providinginformation on the Summer Time (i.e., the Daylight Savings Time). Thetime_zone field corresponds to a (5×8)-bit field indicating the timezone, in which the transmitting system (or transmitter) transmitting thecorresponding broadcast stream is located.

FIG. 23 illustrates segmentation and encapsulation processes of aservice map table (SMT) according to the present invention.

According to the present invention, the SMT is encapsulated to UDP,while including a target IP address and a target UDP port number withinthe IP datagram.

More specifically, the SMT is first segmented into a predeterminednumber of sections, then encapsulated to a UDP header, and finallyencapsulated to an IP header. In addition, the SMT section providessignaling information on all virtual channel included in the MH ensembleincluding the corresponding SMT section. At least one SMT sectiondescribing the MH ensemble is included in each RS frame included in thecorresponding MH ensemble. Finally, each SMT section is identified by anensemble_id included in each section. According to the embodiment of thepresent invention, by informing the receiving system of the target IPaddress and target UDP port number, the corresponding data (i.e., targetIP address and target UDP port number) may be parsed without having thereceiving system to request for other additional information.

FIG. 24 illustrates a flow chart for accessing a virtual channel usingFIC and SMT according to the present invention.

More specifically, a physical channel is tuned (S501). And, when it isdetermined that an MH signal exists in the tuned physical channel(S502), the corresponding MH signal is demodulated (S503). Additionally,FIC segments are grouped from the demodulated MH signal in sub-frameunits (S504 and S505).

According to the embodiment of the present invention, an FIC segment isinserted in a data group, so as to be transmitted. More specifically,the FIC segment corresponding to each data group described serviceinformation on the MH ensemble to which the corresponding data groupbelongs. When the FIC segments are grouped in sub-frame units and, then,deinterleaved, all service information on the physical channel throughwhich the corresponding FIC segment is transmitted may be acquired.Therefore, after the tuning process, the receiving system may acquirechannel information on the corresponding physical channel during asub-frame period. Once the FIC segments are grouped, in S504 and S505, abroadcast stream through which the corresponding FIC segment is beingtransmitted is identified (S506). For example, the broadcast stream maybe identified by parsing the transport_stream_id field of the FIC body,which is configured by grouping the FIC segments.

Furthermore, an ensemble identifier, a major channel number, a minorchannel number, channel type information, and so on, are extracted fromthe FIC body (S507). And, by using the extracted ensemble information,only the slots corresponding to the designated ensemble are acquired byusing the time-slicing method, so as to configure an ensemble (S508).

Subsequently, the RS frame corresponding to the designated ensemble isdecoded (S509), and an IP socket is opened for SMT reception (S510).

According to the example given in the embodiment of the presentinvention, the SMT is encapsulated to UDP, while including a target IPaddress and a target UDP port number within the IP datagram. Morespecifically, the SMT is first segmented into a predetermined number ofsections, then encapsulated to a UDP header, and finally encapsulated toan IP header. According to the embodiment of the present invention, byinforming the receiving system of the target IP address and target UDPport number, the receiving system parses the SMT sections and thedescriptors of each SMT section without requesting for other additionalinformation (S511).

The SMT section provides signaling information on all virtual channelincluded in the MH ensemble including the corresponding SMT section. Atleast one SMT section describing the MH ensemble is included in each RSframe included in the corresponding MH ensemble. Also, each SMT sectionis identified by an ensemble_id included in each section.

Furthermore each SMT provides IP access information on each virtualchannel subordinate to the corresponding MH ensemble including each SMT.Finally, the SMT provides IP stream component level information requiredfor the servicing of the corresponding virtual channel.

Therefore, by using the information parsed from the SMT, the IP streamcomponent belonging to the virtual channel requested for reception maybe accessed (S513). Accordingly, the service associated with thecorresponding virtual channel is provided to the user (S514).

FIG. 25 illustrates a block diagram showing a general structure of adigital broadcasting receiving system according to another embodiment ofthe present invention;

Referring to FIG. 25, the reception system according to anotherembodiment of the present invention includes a baseband processor 100, amanagement processor 200, and a presentation processor 300.

The baseband processor 100 includes an operation controller 110, a tuner120, a demodulator 130, an equalizer 140, a known sequence detector 150,a Mobile Handheld block decoder 160, a primary Reed-Solomon (RS) framedecoder 170, a secondary RS frame decoder 180, and a signaling decoder190. In this case, the operation controller 110, the tuner 120, thedemodulator 130, the equalizer 140, the known sequence detector 150, theMobile Handheld block decoder 160, the primary RS frame decoder 170, thesecondary RS frame decoder 180, and the signaling decoder 190 shown inFIG. 25 correspond to the operation controller 110, the tuner 120, thedemodulator 130, the equalizer 140, the known sequence detector 150, themobile handheld block decoder 160, the primary RS frame decoder 170, thesecondary RS frame decoder 180, and the signaling decoder 190 shown inFIG. 1, respectively. Detailed descriptions of the above-mentionedcomponents of FIG. 25 are equal to those of FIG. 1, such that they willherein be omitted for the convenience of description.

The management processor 200 includes an MH physical adaptationprocessor 210, an IP network stack 220, a streaming handler 230, an SIhandler 240, a file handler 250, a MIME (Multipurpose Internet MailExtensions) type handler 260, an ESG handler 270, an ESG decoder 280, astorage unit 290. In this case, the IP network stack 220, the streaminghandler 230, the SI handler 240, the file handler 250, the MIME typehandler 260, the ESG handler 270, the ESG decoder 280, and the storageunit 290 shown in FIG. 25 correspond to the IP network stack 220, thestreaming handler 230, the SI handler 240, the file handler 250, theMIME type handler 260, the ESG handler 270, the ESG decoder 280, and thestorage unit 290 shown in FIG. 1. Detailed descriptions of theabove-mentioned components of FIG. 25 are equal to those of FIG. 1, suchthat they will herein be omitted for the convenience of description.

The MH physical adaptation processor 210 may include a primary RShandler 211, a secondary RS frame handler 212, a Generic StreamEncapsulation (GSE) handler 2513, a TPC handler 214, an FIC handler 215,and a physical adaptation control signal handler 216.

The primary RS frame handler 211 receives a primary RS frame from theprimary RS frame decoder 170 of the baseband processor 100, divides thereceived primary RS frame into Transport Packets (TPs) used as rowunits, and outputs the divided TPs to the GSE handler 2513.

The secondary RS frame handler 212 receives a secondary RS frame fromthe secondary RS frame decoder 180 of the baseband processor 100,divides the received secondary RS frame into transport packets (TPs)used as row units, and outputs the divided TPs to the GSE handler 2513.

The GSE handler 2513 extracts the GSE packet from the TPs received fromthe primary and secondary RS frame handlers 211 and 212, and calculatesan IP datagram from the extracted GSE packet. The GSE handler 2513outputs the IP datagram to the IP network stack 220.

The TPC handler 214, the FIC handler 215, and the physical adaptationcontrol signal handler 216 shown in FIG. 25 correspond to the TPChandler 214, the FIC handler 215, and the physical adaptation controlsignal handler 216 shown in FIG. 1, respectively. Detailed descriptionsof the above-mentioned components of FIG. 25 are equal to those of FIG.1, such that they will herein be omitted for the convenience ofdescription.

The presentation processor 300 includes an A/V decoder 310, a displaymodule 320, a presentation controller 330, a channel service manager340, and an application manager 350. In this case, the A/V decoder 310,the display module 320, the presentation controller 330, the channelservice manager 340, and the application manager 350 shown in FIG. 25correspond to the A/V decoder 310, the display module 320, thepresentation controller 330, the channel service manager 340, and theapplication manager 350 shown in FIG. 1. Detailed descriptions of theabove-mentioned components of FIG. 25 are equal to those of FIG. 1, suchthat they will herein be omitted for the convenience of description.

FIG. 26 is a structural diagram illustrating a Reed Solomon (RS) frameaccording to another embodiment of the present invention.

Referring to FIG. 26, the RS frame according to the present inventionmay include at least one GSE packet. If the at least one GSE packet iscontained in the RS frame, there is no need for the RS frame to have anadditional header for discriminating individual GSE packets.

There may be an allocation process for allowing one row of the RS frameto have one GSE packet. In this case, the RS frame includes 187 rows,such that it may include 187 GSE packets. If 11 rows of the RS frame areallocated to have one GSE packet, the RS frame may include 17 GSEpackets.

The individual rows of the RS frame have variable lengths, such that onerow of the RS frame may be allocated to a GSE BB (Base Band) frame. Inother words, the GSE BB frame may construct one row of the RS frame. Inthis case, a header of the GSE BB frame is contained in one row of theRS frame, such that the resultant one row of the RS frame can beconstructed. The GSE BB frame header may be deleted from one row of theRS frame, such that the resultant one row of the RS frame can beconstructed. Although the GSE BB frame header is deleted, the GSE packetmay be extracted from the GSE BB frame on the basis of a header of afirst GSE packet contained in the GSE BB frame. The GSE BB frameindicates a frame defined on a physical layer including at least one RSpacket.

FIG. 27 shows the relationship between Protocol Data Units (PDUs) and aGeneric Stream Encapsulation (GSE) packet according to the presentinvention.

Referring to FIG. 27, the PDUs defined on the network layer may becontained in a data field of the GSE packet. In this case, one GSEpacket may include at least one PDU, and a plurality of GSE packets mayinclude a single PDU. If the single PDU is contained in the several GSEpackets and is then encapsulated in the GSE packet, PDU fragmentationmay be conducted. When the PDU is calculated from the GSE packet, a PDUreassembly may be conducted. For example, an IP datagram or an Ethernetframe may be used as an example of the PDU.

The GSE packet may be contained in a Base Band (BB) frame. One GSRpacket may be contained in one BB frame, and several GSE packets may becontained in one BB frame.

FIG. 28 shows a header of the GSE packet according to the presentinvention.

Referring to FIG. 28, the GSE packet header may include at least one ofa Start_Indicator(S) field, an End_Indicator(E) field, aLabel_Type_Indicator(LT) field, a GSE_Length field, a Frag_ID field, aTotal_Length field, a Protocol_Type field, a Label field, and anExtension_Header_Bytes field. The Start_Indicator(S) field may includespecific information indicating a start part of the encapsulated PDU inthe GSE packet, and may have the size of one bit. The End_Indicator(E)field may include specific information indicating the end of theencapsulated PDU in the GSE packet, and may have the size of one bit.The Label_Type_Indicator(LT) field may include padding information, andmay have the size of 2 bits. The GSE_Length field may include specificinformation indicating the length of the GSE packet, and may have thesize of 12 bits. The Frag_ID field may include specific informationindicating whether the PDU fragment is contained in the GSE packet, andmay have the size of 1 byte. If the Start_Indicator(S) field and theEnd_Indicator(E) field are established, the Frag_ID field may includespecific information indicating the absence of the PDU fragment in theGSE packet. The Total_Length field may be contained in the header of theGSE packet including a first fragment of the fragmented PDU, may includetotal length information of the fragmented PDU, and may have the size of2 bytes. The Protocol_Type field may include specific informationindicating a type of the payload delivered by the PDU contained in theGSE packet, and may have the size of 2 bytes. The Label field mayinclude label information used for an addressing operation, and may havethe size of 3/6 bytes. The Extension_Header_Bytes may be reserved forthe extended header format, and may have the size of 2 bytes or the sizeof at least 2 bytes.

If several GSE packets include one PDU, the GSE handler 2513 mayreassemble PDU fragments contained in the several GSE packets on thebasis of information contained in the Start_Indicator(S) field, theEnd_Indicator(E) field, the Frag_ID field, and the Total_Length field.That is, the GSE handler 2513 may extract PDU fragments from individualGSE packets from a first GSE packet including start information of theencapsulated PDU in the SE packet to the last GSE packet including endinformation of the encapsulated PDU in the GSE packet, and mayreassemble the extracted PDU fragments, such that it may calculate thePDU. The GSE handler 2513 may check the size of the reassembled PDU onthe basis of the information contained in the Total_Length field, andmay check a GSE packet located between the first GSE packet includingstart information of the PDU and the last GSE packet including endinformation of the encapsulated PDU in the GSE packet based on theFrag_ID field.

FIG. 29 is a conceptual diagram illustrating a method for constructingthe GSE packet according to the present invention.

Referring to FIG. 29, a Real-time Transport Protocol (RTP) packet isencapsulated into a User Datagram Protocol (UDP) packet in order toconstruct one GSE packet. The UDP packet is encapsulated into the IPpacket. The IP packet is encapsulated into the GSE packet. The BB frameis formed by the GSE packet. In this case, the RTP packet may include aheader of 12 bytes and a payload, and this payload may include mobileservice data.

The GSE packet may include the PDU header having a total length of 40bytes, for example, the RTP packet's header of 12 bytes, the UDPpacket's header of 8 bytes, and the IP packet's header of 20 bytes.Therefore, a bandwidth occupied by a network for transmitting actualbroadcast contents is reduced.

In accordance with this embodiment of the present invention, headerinformation contained in the PDU contained in the GSE packet iscompressed, and the compressed header information is stored. Forexample, a Robust Header Compression (ROHC) may be used to compress theabove PDU header information. The ROHC may include a variety ofexemplary header compression methods, for example, a UnidirectionalMode, a Bidirectional Optimistic Mode, and a Bidirectional ReliableMode. The Bidirectional Optimistic Mode and the Bidirectional ReliableMode may transmit a feedback message for indicating whether or notreception data is correctly received to a compression part forperforming the data compression. Otherwise, the Unidirectional Mode maynot transmit the feedback message to the compression part. Therefore,the Bidirectional Optimistic Mode and the Bidirectional Reliable Modemay transmit the feedback information to the compression part, such thatthey may compress the header more effectively and reliably than theUnidirectional Mode.

The PDU header of 40 bytes contained in the GSE packet may be compressedto 3 bytes or 4 bytes on the basis of the ROHC algorithm.

If the header of the PDU contained in the GSE packet is compressed, theGSE handler 2513 may extract the header of the compressed PDU from theGSE packet, and may recover the extracted header of the compressed PDU,such that it may calculate the PDU.

FIG. 30 is a flow chart illustrating a data processing method accordingto the present invention.

Referring to FIG. 30, one physical channel is selected or changed atstep S3000. The selected physical channel is tuned at step S3010. Abroadcast signal in which main service data and mobile service data aremultiplexed is demodulated at step S3020. In this case, a digitalbroadcasting system for use in the above-mentioned data processingmethod may acquire high-speed data channel information indicating arelationship between the ensemble of the mobile service data and avirtual channel from the demodulated broadcast signal.

The digital broadcasting system may detect a mobile service data framefrom the demodulated broadcast signal using the high-speed data channelinformation at step S3030. In this case, the RS frame may be detected asthe mobile service data frame as an example.

The detected mobile service data frame may be scanned in row units atstep S3040. In this case, the detected mobile service data frame may bestored in a buffer, and the stored mobile service data frame may be readin row units.

The digital broadcasting system may extract the GSE packet from themobile service data frame at step S3050. In this case, the BB frame mayconstruct one row of the mobile service data frame. In this case, thedigital broadcasting system may extract at least one GSE packetcontained in one BB frame from one row of the mobile service data frame.

The digital broadcasting system may calculate the IP datagram from theextracted GSE packet at step S3060. In this case, if data contained inthe PDU header in total data contained in the above GSE packet iscompressed data, the compressed data is recovered such that the IPdatagram can be calculated. The digital broadcasting system maycalculate the IP datagram from one or two GSE packets. If the IPdatagram is calculated from at least two GSE packets, IP datagramfragments contained in each GSE packet are reassembled such that the IPdatagram is calculated.

As apparent from the above description, the digital broadcasting systemand the data processing method according to the present invention havestrong resistance to any errors encountered when mobile service data istransmitted over a channel, and can be easily compatible with theconventional receiver. The digital broadcasting system and the dataprocessing method according to the present invention can normallyreceive mobile service data without any errors over a poor channel whichhas lots of ghosts and noises. The digital broadcasting system and thedata processing method according to the present invention insert knowndata at a specific location of a data zone, and perform signaltransmission, thereby increasing the reception (Rx) performance under ahigh-variation channel environment. Specifically, the digitalbroadcasting system and the data processing method according to thepresent invention can be more effectively used for mobile phones ormobile receivers, channel conditions of which are excessively changedand have weak resistances to noise.

Also, the digital broadcasting system and the data processing method canquickly access services provided to mobile service data, when the mobileservice data is multiplexed with main service data and the multiplexedresultant data is transmitted.

It will be apparent to those skilled in the art that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

1. A method of processing broadcast data in a receiver, the methodcomprising: receiving a broadcast signal including service data for aservice, first signaling data to enable fast service acquisition andsecond signaling data that include transmission parameters,;demodulating the received broadcast signal; decoding the first signalingdata in the demodulated broadcast signal; decoding the second signalingdata in the demodulated broadcast signal; and decoding the service datain the demodulated broadcast signal based on at least the firstsignaling data or the second signaling data, wherein the decoded servicedata are included in a baseband frame, wherein the baseband frameincludes one or more data packets that include an Internet Protocol (IP)packet or a fragment of the IP packet, the IP packet including acompressed header and the service data, wherein the first signaling datainclude information for locating where service layer signaling iscarried, and wherein the service layer signaling includes accessinformation of the service data.
 2. The method of claim 1, furthercomprising: extracting the one or more data packets from the basebandframe; and decompressing the compressed header of the IP packet includedin the extracted one or more data packets in order to reconstruct anoriginal IP packet.
 3. The method of claim 2, wherein the compressedheader is decompressed based on a Robust Header Compression (ROHC)scheme.
 4. The method of claim 1, wherein one of the one or more datapackets includes the IP packet or the fragment of the IP packet.
 5. Themethod of claim 4, wherein a header of each of the one or more datapackets includes information indicating whether the corresponding datapacket carries a part of the IP packet and information to reassemblefragments belonging to the IP packet.
 6. A receiver for processingbroadcast data, the receiver comprising: a tuner to receive a broadcastsignal including service data for a service, first signaling data toenable fast service acquisition and second signaling data that includetransmission parameters; a demodulator to demodulate the receivedbroadcast signal; and a decoder to: decode the first signaling data inthe demodulated broadcast signal; decode the second signaling data inthe demodulated broadcast signal; and decode the service data in thedemodulated broadcast signal based on at least the first signaling dataor the second signaling data, wherein the decoded service data areincluded in a baseband frame, wherein the baseband frame includes one ormore data packets that include an Internet Protocol (IP) packet or afragment of the IP packet, the IP packet including a compressed headerand the service data, wherein the first signaling data includeinformation for locating where service layer signaling is carried, andwherein the service layer signaling includes access information of theservice data.
 7. The receiver of claim 6, further comprising: a handlerto extract the one or more data packets from the baseband frame anddecompress the compressed header of the IP packet included in theextracted one or more data packets in order to reconstruct an originalIP packet.
 8. The receiver of claim 7, wherein the compressed header isdecompressed based on a Robust Header Compression (ROHC) scheme.
 9. Thereceiver of claim 6, wherein one of the one or more data packetsincludes the IP packet or the fragment of the IP packet.
 10. Thereceiver of claim 9, wherein a header of each of the one or more datapackets includes information indicating whether the corresponding datapacket carries a part of the IP packet and information to reassemblefragments belonging to the IP packet.